Great suite of test cases, can we think of some more edge cases to test, making sure the function can handle tricky arguments?

Thank you for your review. I have added several edge cases to the tests. Please let me know if I've understood your question correctly.

Great Dipa yeah this is exactly what I meant, here you are testing all possible edge cases

Thank you!

Readability and naming are spot on!

I'm curious about the control flow choices here. Could you share why you opted for the else if chain and wrapped the final return in an else block?

There are multiple conditions to check that's why I used else if inside if...else statement. I wrapped the final return in else cause none of the above conditions are true for "th", so for "th" else block will execute. That's my thought actually.

That completely makes sense and your logic works perfectly, but we can still make it a bit simpler.

• We can avoid the separate first if block and check for the exceptions directly inside each rule using the && operator.
  Something like this: if (lastDigit === 1 && lastTwoDigits !== 11) return \${num}st;``

• When an if statement contains a return, you can safely drop the "else" from else if to make it more readable.
  Because return stops the function entirely, if all ifs fail, the program naturally drops down to the lines below. This means we can remove the final else wrapper as well and just leave the 'th' return at the very bottom as our default."

Does this make sense to you?

oh! yeah I got your point. Should I have to change the style of the code?